
######################################################################################
#  General flags
#

SC_VERIFY  FALSE		# TRUE  means  that the verification shall be  
				# performed within SCT/SC
SC_ENCRYPT FALSE		# TRUE  means  that the RSA encryption shall be  
				# performed within SCT/SC


######################################################################################
#
#  Application .sc
#

PSE	       .sc		# PSE name used within SECUDE

APPLICATION_ID D27600000701	# application identifier used within STARCOS

NO_OF_DES_KEYS	1		# Max. Number of DES keys which can be 
				# installed for this PSE


#-------------------------------------------------
#  Key Objects (for a PSE with one keypair)
#-------------------------------------------------
#
#  The following table assigns object names, as they are used by the application 
#  program at the SEC-interface, to Key-IDs as they are used by STARCOS.
#
#
#         Object Name     Object Type  Key-Id 

OBJECT    SKnew             SC_KEY       1              
OBJECT    SKold             SC_KEY       2              


#-------------------------------------------------
#  File Objects (for a PSE with one keypair)
#-------------------------------------------------
#
#  The following table serves three purposes:
#
#  1. It assigns object names, as they are used by the application program at the
#     SEC-interface, to File-IDs as they are used by STARCOS.
#  2. It defines a maximum size (in octets) for each object as this is needed by 
#     STARCOS. This size is only used at object creation time. The size should be 
#     a multiple of 32 octets. For each file 32 octets for internal purposes are 
#     to be added.
#     The total size for a PSE with one keypair must not exceed 2688 octets.
#  3. For the transfer of objects between SC and host, a secure messaging mode
#     can be defined.
#     The following secure messaging modes are possible:
#  
#     NONE   No secure messaging (default mode)
#     INTG   integrity-protected transfer of objects between SC and host
#     CONF   confidentiality-protected transfer of objects  between SC and host
#     COMB   INTG + CONF
#
#
#         Object Name     Object Type  File-Id   Max. Size      Secure Messaging Mode

OBJECT    SCToc             SC_FILE       1   	    416    	       NONE   
OBJECT    Cert              SC_FILE  	  2         512                NONE    
OBJECT    PKRoot            SC_FILE       3         512                NONE     
OBJECT    FCPath            SC_FILE       4         832                NONE      
OBJECT    QuipuPWD          SC_FILE       5          32                NONE      







######################################################################################
#
#  Application .sc2
#

PSE	    .sc2		# PSE name used within SECUDE

APPLICATION_ID D27600000701	# application identifier used within STARCOS


#-------------------------------------------------
#  Key Objects (for a PSE with two keypairs)
#-------------------------------------------------
#
#  The following table assigns object names, as they are used by the application 
#  program at the SEC-interface, to Key-IDs as they are used by STARCOS.
#
#
#         Object Name     Object Type  Key-Id 

OBJECT    SignSK            SC_KEY       1              
OBJECT    DecSKnew          SC_KEY       2              
OBJECT    DecSKold          SC_KEY       3              


#-------------------------------------------------
#  File Objects (for a PSE with two keypairs)
#-------------------------------------------------
#
#  The following table serves three purposes:
#
#  1. It assigns object names, as they are used by the application program at the
#     SEC-interface, to File-IDs as they are used by STARCOS.
#  2. It defines a maximum size (in octets) for each object as this is needed by 
#     STARCOS. This size is only used at object creation time. The size should be 
#     a multiple of 32 octets. For each file 32 octets for internal purposes are 
#     to be added.
#     The total size for a PSE with two keypairs must not exceed 2432 octets.
#  3. For the transfer of objects between SC and host, a secure messaging mode
#     can be defined.
#     The following secure messaging modes are possible:
#  
#     NONE   No secure messaging (default mode)
#     INTG   integrity-protected transfer of objects between SC and host
#     CONF   confidentiality-protected transfer of objects  between SC and host
#     COMB   INTG + CONF
#
#
#         Object Name     Object Type  File-Id   Max. Size      Secure Messaging Mode

OBJECT    SCToc             SC_FILE       1         480  	       NONE
OBJECT    SignCert          SC_FILE       2         512                NONE     
OBJECT    EncCert           SC_FILE       3         512                NONE     
OBJECT    PKRoot            SC_FILE       4         512                NONE     
OBJECT    QuipuPWD          SC_FILE       6          32                NONE      







######################################################################################
#
#  CA-PSE .caSC/.capse
#
#
#PSE	    .caSC/.capse   	# PSE name used within SECUDE
#
#APPLICATION_ID D27600000701	# application identifier used within STARCOS
#
#NO_OF_DES_KEYS	1		# Max. Number of DES keys which can be 
#				# installed for this PSE
#
#
#-------------------------------------------------
#  Key Objects (for a PSE with one keypair)
#-------------------------------------------------
#
#  The following table assigns object names, as they are used by the application 
#  program at the SEC-interface, to Key-IDs as they are used by STARCOS.
#
#
#         Object Name     Object Type  Key-Id 
#
#OBJECT    SKnew             SC_KEY       1              
#OBJECT    SKold             SC_KEY       2              
#
#
#-------------------------------------------------
#  File Objects (for a PSE with one keypair)
#-------------------------------------------------
#
#  The following table serves three purposes:
#
#  1. It assigns object names, as they are used by the application program at the
#     SEC-interface, to File-IDs as they are used by STARCOS.
#  2. It defines a maximum size (in octets) for each object as this is needed by 
#     STARCOS. This size is only used at object creation time. The size should be 
#     a multiple of 32 octets. For each file 32 octets for internal purposes are 
#     to be added.
#     The total size for a PSE with one keypair must not exceed 2688 octets.
#  3. For the transfer of objects between SC and host, a secure messaging mode
#     can be defined.
#     The following secure messaging modes are possible:
#  
#     NONE   No secure messaging (default mode)
#     INTG   integrity-protected transfer of objects between SC and host
#     CONF   confidentiality-protected transfer of objects  between SC and host
#     COMB   INTG + CONF
#
#
#         Object Name     Object Type  File-Id   Max. Size      Secure Messaging Mode
#
#OBJECT    SCToc             SC_FILE       1   	     416    	        NONE   
#OBJECT    Cert              SC_FILE  	   2         512                NONE    
#OBJECT    PKRoot            SC_FILE       3         512                NONE 
#OBJECT    SerialNumber      SC_FILE       4          32                NONE 
#OBJECT    CrlSet	     SC_FILE       5         128                NONE 


